You're still explaining the solution, not the problem. To be clear, we broadly *like* the collateral effects, that's why we're happy with the planned changes. If you want to convince us to change course, the most effective thing to do is to convince us that our *goals* need improvement, rather than simply pitching alternate implementations.

Ahem. As one that "mutters" I have a question.

Has anyone proposed having characters designate a "home region" where jump fatigue isn't generated? This could have at least a multiple month reset timer so changing couldn't be exploited.

The fact that people are trying to mitigate this nerf is not an indication that the nerf was crap - it's an indication that they refuse to adapt to the new conditions, nothing more.

The Jita monument awaits your attention.

Ok, lets do this again for the people who don't get it. To be fair I reread the dev blog before I wrote this and I will say that somewhere along the line some info may have gotten lost. I don't see a clear explanation of what happens to fatigue when you get below 10 minutes. This is because fatigue was originally a number representing an amount of time, not an actual amount of time. In switching the explanation over to minutes they seem to have left out the strict explanation of this breakpoint. To be clear, the following statement from the dev blog infers what you need to know but doesn't state it very clearly:

Jump fatigue has a minimum amount of 10 x (1 + (LY traveled)) minutes after a jump. Jump fatigue has a maximum amount of 30 days.

That 10 is a representation of minutes. Since 10 is the minimum they use in the calculation that means that jumping during the last 10 minutes of fatigue is the same as jumping at 0 minutes of fatigue. With that explained clearly, here we go.

Starting Fatigue: 0
Starting Jump Cooldown: 0

All jumps will be 5LY.

Cooldown after first jump: 6 minutes (this is the minimum for any jump)
Fatigue after first jump: 60 minutes

So you wait the 6 minutes, because you have to. Then we break into the two scenarios. Scenario A will be waiting until the optimum moment to jump to minimize fatigue. Scenario B will just jump when the cooldown timer ends.

Scenario A Jump 2: Knowing that the best time to jump is when you have 10 minutes of fatigue or less, you wait 50 minutes after the first jump. That's an additional 44 minutes of waiting past the cooldown for a clean jump.

Distance Traveled: 10LY
Jump Cooldown: 6 minutes
Fatigue: 60 minutes
Time spent: 50 minutes


Scenario B Jump 2: Not caring about the effect of the fatigue mechanic, you jump after the 6 minute cooldown timer is up. That means you jumped with 54 minutes of fatigue remaining.

Distance Traveled: 10LY
Jump Cooldown: 6 minutes
Fatigue: 324 minutes (5.4 hours)
Time spent: 6 minutes


Scenario A Jump 3: Once again you repeat the 50 minute wait, which is 44 minutes more than your jump cooldown.

Distance Traveled: 15LY
Jump Cooldown: 6 minutes
Fatigue: 60 minutes
Time spent: 100 minutes (1.66 hours)


Scenario B Jump 3: Still not caring about the effect of the fatigue mechanic, you jump after the 6 minute cooldown timer is up. That means you jumped with 318 minutes of fatigue remaining.

Distance Traveled: 15LY
Jump Cooldown: 31.8 minutes (10 % of fatigue before jump, or 6, whichever is higher)
Fatigue: 1908 minutes (31.8 hours)
Time spent: 12 minutes


Summary: Max sustained jump speed is now 5LY/50 minutes for carriers/dreads/supers/titans. You can go faster than that, but after the 3rd jump things get slow due to the cooldown blooming past the 6 minute minimum.

If you didn't notice the pattern by now, you should always wait your fatigue down to 10 minutes or less before you jump unless it's absolutely necessary. Things get multiplicative quickly if you don't.

If its not worth the time, then obviously it wasn't important enough. No more,"Iforgot that module back in highsec, I'll be back in 5 minutes."

Also: Marxist? explanation please